Globalization management system and method therefor

ABSTRACT

A globalization management system for managing resources of multiple interrelated data sources corresponding to a plurality of sites through a communications network is provided. The system includes a plurality of target application interfaces respectively coupled to the interrelated data sources through the network. Each interface includes systems for converting a protocol of the respective data source to a predetermined protocol, and the predetermined protocol to the protocol of the respective data source. The system further includes a global management engine coupled to the plurality of target application interfaces. The engine includes a site-to-site relationship manager, a system for reading current content data from the interrelated data sources, a system for comparing the current content data with prior content data, and a project manager for transferring the data identified as a content change to at least one subscriber site.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/609,293 filed Sep. 11, 2012, which is a continuation of U.S.patent application Ser. No. 13/019,980 filed Feb. 2, 2011, which is acontinuation of U.S. patent application Ser. No. 10/003,315 filed Dec.6, 2001, which claims priority to U.S. provisional patent applicationNo. 60/262,073 filed Jan. 18, 2001. The disclosures of the foregoing areincorporated herein by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

This invention directs itself to a system for managing the resourcesdefined as code, content and graphics, of multiple interrelated andmultilingual web sites. Further, this invention directs itself to amethod for automatically updating the resources of web sites identifiedas subscribers responsive to changes in a resource on one or more sourceor provider sites. More in particular, this invention is directed to asystem which provides the infrastructure for managing the deployment ofmultilingual resources across a network of globalized web sites. Stillfurther, this invention provides a method for coordinating resources andmanaging globalization activity updates across multiple, multilingualweb sites. Still more in particular, this invention provides the meansto detect changes throughout a client's network of globalized web sites,automatically triggers localization of a global resource according topredetermined schedules, processes and customer-defined business rules,and then updates the subscriber sites with the updated resources,directly, translated, or in a localized form.

Prior Art

Content management systems are known in the art. Heretofore, suchsystems, such as provided by VIGNETTE, INTERWOVEN, DOCUMENTUM, andothers provided the means to manage the creation of content andresources for web site content for a particular site. However, suchsystems could not integrate a globalized network of web sites havingnon-uniform interrelationships there between.

The present invention overcomes the limitations of the prior art byproviding a globalization management system that complements existingcontent management systems to handle global content changes or updateswith a minimum of manual intervention. Yet, the globalization managementsystem of the present invention allows for defining the relationshipsbetween a company's multiple multilingual web sites, as well asadditions and deletions of web sites. Additionally, the resources whichare monitored can be added to, deleted, as well as provide for editingof tasks associated with various types of content.

SUMMARY OF THE INVENTION

A system for managing the resources of multiple interrelated andmultilingual web sites is provided. The system provides for automaticdetection of updates at particular web sites, identifies the resource asrequiring translation, or other changes, such as localization, andtransfers the resource, in its translated or localized form toidentified subscriber web sites. The system provides the means formanaging complex interrelationships between multiple web sites of uuser, which may be multilingual, or may cater to an audience requiring aparticular presentation format or resource.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating applications of the globalizationmanagement system of the present invention;

FIG. 2 is a more detailed block diagram of the present invention;

FIG. 3 is a diagram illustrating an application of the presentinvention;

FIG. 4 is a block diagram representing the data flow within the presentinvention;

FIG. 5 is a flowchart illustrating the present invention's resourcestaging scheme of the present invention;

FIG. 6 is a flowchart illustrating the resource globalization process ofthe present invention;

FIG. 7 is a flowchart illustrating the globalization analysis andevaluation process of the present invention;

FIG. 8 is a flowchart illustrating the interim nationalization processof the present invention;

FIG. 9 is a block diagram illustrating the target application interfacearchitecture of the present invention;

FIG. 10 is a flowchart illustrating the target application interfacecustomization process of the present invention;

FIG. 11 is a flowchart illustrating the globalization management set-upprocess of the present invention;

FIG. 12 is a flowchart illustrating the globalization management processof the present invention;

FIG. 13 is a flowchart illustrating the user management process of thepresent invention;

FIG. 14 is a schematic diagram illustrating a provider and subscribermodel for user with the present invention;

FIG. 15 is a flowchart illustrating the site-to-site relationshipmanagement process of the present invention;

FIG. 16 is a flowchart illustrating the project management process ofthe present invention;

FIG. 17 is a flowchart illustrating the project action process of thepresent invention; and,

FIG. 18 is a flowchart illustrating the global resource translationprocess of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A system for managing the resources of multiple interrelated web sitesis provided to provide automatic detection of resource updates atparticular web sites, identified as resource providers, transferring theupdates to other sites, identified as subscribers, wherein thetransferred resource may be translated and/or localized, as required. Asillustrated in FIG. 1, each entity, company X, Y, and Z, is providedwith a globalization management system 200 x, 200 y, 200 z,respectively. Each of the company's web server systems (web servers) 10,12, 14 communicates through a respective Intranet 30 x, 30 y, 30 z withthe globalization management system 200 x, 200 y, 200 z. Theglobalization management system 200 x, 200 y, 200 z has the ability tointerface with the local resource management/database system used withinthe web servers 10, 12 14, whether it is a VIGNETTE system, INTERWOVENsystem, DOCUMENTUM, or others. When web page content requirestranslation for use in one of the company's foreign language web sites,the globalization management system 200 x, 200 y, 200 z communicateswith an electronic translation portal (ETP) 210 through a globalcomputer network (Internet) 20. Thus, the system provides the means bywhich multilingual and multi-site web-site globalization can beefficiently and substantially automatically managed.

A more detailed view of the globalization management system is furtherillustrated in FIG. 2. An individual responsible for administration of acompany's web sites communicates with the global contact managementsystem utilizing a terminal 202 utilizing web browser software. Theterminal 202 communicates with a server 204 which receives data from theagent 208. Agent 208 communicates through the Internet with theelectronic translation portal 210 as well as a remote target applicationinterface 222, which is considered a backend data source for the system.Data being transmitted to server 204 from agent 208 is in the form ofpresentation 206, which is much like a web page. An active server pages(ASP) or Java server pages (JSP) template is utilized to collectinformation from the database and create presentation 206 which ispresented to the server 204 for transmission to the terminal 202, oralternately, to the electronic translation portal 210, through theInternet, in order to have that information translated for the operatorof terminal 202.

In use, as shown in the diagram of FIG. 3, a Company X has a web server10 which provides a web site 102 in the United States, a web site 104 inJapan, and at least one other web site 106 in another country. Theglobalization management system 200 x maintains the resourcerelationships between the multiple sites by automatically updating,translating and localizing the data added to those sites identified asresource providers for incorporation in the subscriber sites. In thefollowing example, Company X is a widget manufacturer with its primaryweb site 102 created in English. Utilizing the electronic translationportal 210 through the Internet 20 one or more resources of the Englishweb site 102 is translated into Japanese for use on the Japanese site104 and French, for the French site 106. Company X has manufacturingplants in the U.S., Japan and France, and therefore each of therespective web sites 102, 104 and 106 is identified as a provider forthe other sites, which also therefore act as subscribers. For instance,if the Company's Japanese site posts an article dealing with possiblechanges in Japan's laws concerning how widgets are manufactured or soldin that country, that information may be important to widget productionand imports/exports in the United States and France. Therefore, with theJapanese site acting as provider, the globalization management system200 x will identify the newly posted article on the Japanese site,transmit that resource to the electronic translation portal 210, andupon returned receipt of the translated resource, globalizationmanagement system 200 x will then update the U.S. and French sitesappropriately. In other cases, wherein content is strictly local, suchas pricing or sales associated with locally observed holidays, noprovider/subscriber relationship will exist for that content and anupdate in pricing on the French site will not affect any content oneither the U.S. or Japanese sites. Thus, the globalization managementsystem 200 x allows the subscription and provider relationships betweenthe sites to be set up at different granularities such that items assmall as individual paragraphs in a file and as large as entire websites can have resources copied, translated and localized. Localizationis the adaptation of shared web site resources from the resourceprovider to the subscriber to conform to the local culture and businesscustoms of the subscriber locale. In addition to such content as productpricing, content relating to holiday promotions or containing particularcolloquialisms will need adaptation for local sites, rather than directtranslation. Although each of the web sites 102, 104, 106 includes localcontent editors and reviewers 4, 4′, 4″, use of the globalizationmanagement system 200 x takes care of the problem of updating one sitewith respect to changes made at one of the others.

Turning now to FIG. 4, there is shown the block diagram representing thedata flow within the globalization management system. The globalizationmanager engine 100 communicates with the data sources of the U.S. and,for example, the Japanese web sites through a local target applicationinterface (TAI) 222′ and a remote target application interface 222″,respectively. Each of the respective interfaces 222′, 222″ has an openarchitecture for communicating with the data sources 1021 and 1022 usedby the web site 102 and data sources 1041, and 1042, used by the website 104, respectively. Thus, wherein the Japanese web site is inEnglish, and therefore no translation is needed, the globalizationmanager engine 100 is able to identify changes in a resource, andappropriately transfer such from one data source of one web site to adata source of another.

In FIG. 5, the globalization management system's resource staging schemeis shown. Web site resources are created by individuals. The creation ofa resource goes through a number of stages, beginning with thedevelopment environment 300 wherein web site form and resources evolve.From the development environment, there is next a staging environmentwherein the resource is prepared and arranged. From the stagingenvironment 302, the resource may be then published, from which it thengoes to the production environment 306. The globalization managementsystem 200 can replicate any of those environments, pulling resourcesfrom the development environment,

staging environment, publishing environment or production environment.Thus, the replication can take place in any of blocks 308, 310, 312 or314, depending on the user's desires. The source and target environmentsare a function of such characteristics as the language of the resourceand the culture into which it is targeted. Consider, a web site whichhas been developed in French for the culture in France which must thenbe replicated, to a certain degree, for use in Quebec, Canada. Althoughthe language need not significantly change, there are significantcultural differences which may affect the content.

The flow chart in FIG. 6 will aid in understanding the process ofresource globalization. Beginning from the start block 350, the processbegins with a globalization analysis and evaluation in block 352. Thatprocess is further defined in FIG. 7, and will be discussed in followingparagraphs. From block 352, the flow passes to decision block 354wherein it is determined whether the user's content management systemneeds to be internationalized (able to handle multiple languages). If itrequires internationalization, the flow passes to block 356 (furtherdefined in FIG. 8). Subsequent to internationalization, the flow passesfrom block 356 to decision block 358. If internationalization was notrequired, flow passes from decision block 354 to decision block 358. Inblock 358 it is determined whether target application interfacecustomization is required. Target application interface customizationdeals with the selection of data sources from which the resource isderived, and if customization is required, the flow moves to block 360,which process is further defined in FIG. 10. Subsequent tocustomization, the flow passes to the global content manager setupprocedure identified in block 362. If target application interfacecustomization was not required, the flow passes from block 358 to block362. The globalization manager setup of block 362 deals withconfiguration and initialization of a number of subprocesses that arefurther illustrated in FIG. 11.

From block 362, the flow then passes to block 364 which describes themanagement steps involved with management of global resources. Fromblock 364, the flow passes to block 366 wherein the system hibernates,goes to sleep for a predetermined period. By waiting a predeterminedtime period, the system is allowing time for a resource to be changed onthe source site(s). The time period could be in terms of minutes, hours,days, weeks, etc., whatever would be a reasonable cycle time for thetype of web site, and/or business associated with the web site, that isthe content source. After that predetermined time period, the flow thenpasses to block 368 wherein auto change detection is launched, and flowthen passes to decision block 370. In block 370, it is determinedwhether there has been a change in content on the source site. If therehas been a change, flow passes back to block 364 for managing thatchange. If no change has been detected, flow passes to decision block372 where it is determined whether the user has requested the process tobe shut down. If the process has not been requested to shut down, flowpasses back to block 366 to await the next cycle. If the user hasrequested the shutdown of the process, flow passes to end block 380.

The steps involved in the globalization analysis and evaluation, block352 of FIG. 6, are outlined in the flow chart of FIG. 7. From theresource globalization process, indicated at block 400, the flow passesto block 402 wherein the customer's business approach, web architecture,processes and marketing readiness are analyzed and evaluated. From block402, the flow passes to block 404, wherein it is determined the size ofthe web site and the number of target sites which the customer is tohave, and in what countries they will reside. In block 404, it isdetermined what type of company management systems are to be used andwhether those systems are going to use their own native file format orwhether they are going to integrate with other file formats or any othercontent management systems. From block 404, the flow passes to block406. In block 406, it is determined how many target applications will beneeded to be created or supported, the type of target applicationinterfaces needed, the integration method and the type of databases tobe utilized as well. From block 406, the flow passes to block 408wherein the interrelationships between sites is defined. For example,the U.S. site will subscribe resources into the Japanese site and someresource of the Japanese site may be subscribed to the U.S. site.

From block 408, the flow passes to block 410 wherein it is determinedwhich resource needs to be translated, which resource needs to be copieddirectly, and which content needs to be localized, or handled in somespecial manner or in accordance with particular business rules. Fromblock 410, the flow passes to block 412 where it is decided how thesystem is to be deployed. For example, the customer can use any filemanagement system or word processing system to deploy it, or they mayuse the content management system to deploy it. From block 412, the flowpasses to block 414. In block 414, the local content editor, reviewerand translator are chosen. Those functions may be handled by individualssuch as company employees, outside companies or contractors, or softwarepackages which handle the function. From block 414, the flow passes toblock 416, wherein the customer's software is accessed and evaluated asto its internationalization readiness, such as handling multilingualinput and/or output, different currencies, multiple time zones, etc.From block 416, the flow passes to block 418, wherein the flow isreturned to block 352 of FIG. 6.

In FIG. 8, the process for internationalization is shown. Beginning fromstart block 420, the flow passes to block 422 in which the customer'ssource code is analyzed and evaluated. That evaluation includes ananalysis of the language utilized, the ability to handle differentcurrencies and data information peculiar to any particular locale. Inaddition to the operating software, the user's databases are alsochecked to make sure they are ready and able to store data coming fromworldwide sources. From block 422, the flow passes to decision block424, wherein it is determined whether the database code needs to bechanged. It is important that the database be a unicode database, onewhich can accept data in all languages. If any database is not a unicodedatabase, the flow passes to block 426, wherein the database is modifiedaccordingly. From block 426 the flow passes to decision block 428, asdoes the flow from decision block 424 if no modification is required tothe database. In block 428, it is determined whether the applicationserver code, which may be JAVA, C++ or C, or any other program language,is able to process data from any of the different languages beingsupported by the multiple web site architecture. If the applicationserver code requires modification, the flow passes to block 430 for suchmodification. If no modification is required, flow passes from decisionblock 428 to decision block 432. Likewise, subsequent to modification inblock 430, the flow then passes to decision block 432.

In decision block 432, it is determined whether the client application,i.e. WINDOWS client, UNIX client, etc. can display the local informationproperly. If it cannot, and requires modification, the flow then passesto block 434 wherein it is modified accordingly. If no modification isrequired, the flow passes from decision block 432 to decision block 436.If modification was required, the flow passes from block 434 to decisionblock 436. In decision block 436, the client's front end web-basedclient code is checked to ensure that it is internationally ready. Ifmodification is required, flow passes to block 438, wherein themodifications are made so that the front end web-based client softwarecan process and display data from all of the required languages. If nomodification is required, or subsequent to such modification, the flowpasses to block 440, wherein the flow returns to block 356 of FIG. 6.

The architecture of the target application interface is shown in theblock diagram of FIG. 9. The target application interface 222communicates with the globalization manager engine 100, which accessesthe application content database interface 2221. The application contentdatabase interface accesses (“talks to”) the target (customer's)application content database 230, in which database the customer's webpage content resides. In this manner, the globalization manager engine100, through the application content database interface 2221 and usingan appropriate driver, such as Java Database Connectivity (JDBC) or OpenDatabase Connectivity (ODBC), pulls out the customer's web page content,checks it, and is able to make changes thereto. The application contentdatabase interface 2221 also provides an interface with an XML datasource 232 for transfer of information to the globalization managerengine 100. The target application interface 222 also includes the meansto talk to any content management system, such as through the filters214, 216 and 218, which respectively provide an interface between theVIGNETTE story server 1000, the Interwoven server 1200, and remote website file system 1002 and web site local file system 1202. The datareceived through the filters 214, 216 and 218 is supplied to theglobalization manager engine 100 through a content management systeminterface 212.

Referring now to the flow chart representing the target applicationinterface customization process in FIG. 10, the flow passes from thestarting point 450 to the decision block 452. Decision block 452determines whether the data source is of the Vignette type. If it is,the flow passes to block 460 wherein any target application interfacecustomization is provided, if needed. If it is not a Vignette datasource, the flow passes to decision block 454 wherein it is determinedwhether the data source is an Interwoven type. If the data source is anInterwoven type, the flow passes to block 460. If it is not anInterwoven data source, the flow passes to block 456, wherein it isdetermined whether the data source is a database. If the data source isa database, the flow passes to block 460, otherwise, the flow passes todecision block 458. Decision block 458 determines whether the datasource is a file. If the data source is a file, flow passes to block460. If it is not a file type, the flow passes to block 462, since thedata must be a new type of data source, the flow not having beenpreviously diverted to block 460, and therefore requires the creation ofa new target application interface for that data source. From block 460,and block 462, the flow passes to block 464, wherein the process isreturned to block 360 of FIG. 6.

In FIG. 11, the steps involved in the setup of the globalization managerare shown. From the starting point at block 466, the flow passes toblock 468 wherein the multiple customer web sites are all configured andthe GM server. From block 468, the flow passes to block 470 wherein thetarget application interface is installed and the resource informationis set up. From block 470, the flow passes to block 472. In block 472,the resource sharing and security parameters are set up. From block 472,the flow passes to block 474 wherein the electronic translation portalaccount is set up so that automated translation processing can beaccomplished. One such electronic translation portal is found awww.uniscape.com. From block 474, the flow passes to block 476, whereinthe processing is returned to block 362 of FIG. 6.

In FIG. 12, there is shown the flow chart associated with the globalresource management process. The process contains three steps, usermanagement in block 482, site relationship management in block 484, andproject and work flow management in block 486. From block 486, the flowpasses to block 488, wherein the process flow is returned to block 364of FIG. 6. The processes involved in each of the three steps of blocks482, 484 and 486 are further detailed in FIGS. 13, 15 and 16,respectively.

The user management process is shown in FIG. 13. From the start block490, the flow passes to decision block 492 wherein it is determinedwhether the process is for a new user, or not. If it is not a new user,the flow passes to block 494 wherein the user logs in to the system andthe user's identification is checked. From block 494, the flow passes toblock 496 wherein it is determined whether the user's identification isvalid. If it is not, flow passes back to block 494. If the user'sidentification is valid, the flow then passes to block 518, wherein theprocess is returned to block 482 of FIG. 12.

If in block 492 it is determined that the user is a new user, the flowpasses to block 498 wherein a new user login identification is created.From block 498, the flow passes to decision block 500 wherein it isdetermined whether a new user role is needed. The user's role has to dowith their responsibility associated with the user's system. Forinstance, the user's role may be management of a particular one ofmultiple web sites, or the particular user may be the administrator forall of the user's web sites. Other roles include engineer, developer,translator, workflow administrator, system administrator, projectmanager, etc. If a new user role is not needed, i.e. a predefined roleis to be used, the flow passes to block 502, wherein the role isassigned to the user and then the flow passes to block 494 for theuser's login to the system. If, however, a new user role is needed, theflow passes from decision block 500 to block 504 wherein the new userrole is created. In creating a new role, the user gives the new role aname, such as “localization manager”, and enters a detailed descriptionof the role. From block 504, the flow passes to decision block 506wherein it is determined whether new role responsibilities are needed.For some roles, responsibilities have been predetermined, however, whereresponsibilities of the user differ from those already identified, theother responsibilities can be assigned to a particular role. If noadjustment to the responsibilities is required, the flow passes to block508 wherein the predetermined responsibilities are assigned to the roleand flow then passes to block 502. Where new responsibilities arerequired, the flow passes to block 510 wherein the new roleresponsibilities are created. From block 510, the flow passes todecision block 512 wherein it is determined whether new actions need tobe associated with a particular responsibility. Actions are essentiallyprivileges that the user may be granted for accessing the system,creating or updating a web site, creating or updating just one page of aweb site, or any other action that would be associated with a particularuser management role. Therefore, if no additional actions over thosewhich have been predetermined for particular responsibility arerequired, the flow passes to block 516 wherein those predeterminedactions are assigned to the particular responsibility of the user andthe flow then passes to block 508. If, however, new actions arerequired, then the flow passes to block 514 wherein those actions arecreated for the particular responsibility and then flow passes to block516.

Before discussing the site-to-site relationship management process, itis believed that a review of a provider and subscriber model, like thatshown in FIG. 14, may be beneficial. FIG. 14 depicts a hypotheticalmodel for a large Corporation having a number of web sites worldwide.The Corporation has two main corporate level web sites 40 and 50 whichare identified as providers of resources to many of the other sites 42,44, 45, 52 and 54. A site 52 which may represent a manufacturingoperation of the Corporation is a subscriber to both of the maincorporate level sites 40 and 50, wherein the sites 42, 44 and 45 aresubscribers of the corporate level site 40 and the site 54 is asubscriber of the site 50. The site 44 in addition to being a subscriberof resources from site 40 is also a provider to each of two other sites46 and 48. The site 52 of the manufacturing operation is a provider totwo other sites 56 and 58. Site 58 represents a Japanese operation ofthe Corporation, for example, and therefore some of the resources whichare introduced into that site need to be reflected in the U.S. andEuropean sites, for example. Therefore, the Japanese site 58 is also aprovider site for the sites 52 and 54. Once a model of the relationshipsbetween the sites is established, the process for specifying thesite-to-site relationships for the resource globalization process can beperformed.

Referring now to FIG. 15, there is shown a flow chart for thesite-to-site relationship management process. From the starting point520, the flow passes to decision block 522 wherein it is determinedwhether the user who has logged on has a role which allows them tocreate new sites. If they have such access rights, then the flow passesto block 524 wherein they create the site with its locale information.Locale has four components; language, territory, character coding, andsorting scheme. The character coding may vary with the language in whichthe page is presented. In the U.S., characters are encoded utilizing anASCII coding. In the U.S., the sorting is usually done utilizing adictionary sort routine, wherein upper case characters have precedenceover lower case. The user can specify the sorting scheme in the sitecreation step. From block 524, the flow passes to decision block 526. Ifin decision block 522, the user does not have authority to create asite, then the flow from decision block 522 passes also to decisionblock 526. In decision block 526, it is determined whether the user hasauthority to create a data source. If the user does not have suchauthority, the flow passes to block 530. If the user does have theauthority, the flow passes to block 528 wherein the data source and itsassociated security information are created. In block 528, the flowpasses to block 530. In block 530, the user specifies the necessaryinformation for the target application interface so that it can properlycommunicate with the data source. As previously discussed, the targetapplication interface allows a transfer of files and folders between theglobalization manager and the site's data source.

From block 530, the flow passes to decision block 532 wherein it isdetermined whether the site is to take on the role as a resourceprovider to other sites. If the site is to be a provider, then the flowpasses to block 534. In block 534, the globalization manager workflowdaemon copies the data items from the provider resource data source intothe subscriber's staging area. From block 534, the flow passes to block536. If the site is not a provider, then the flow passes from decisionblock 532 to decision block 536. Decision block 536 determines whetherthe site is a subscriber site. If it is not, the flow passes from block536 to decision block 540. If the site is a subscriber site, then theflow passes to block 538. In block 538, the content sources areidentified. In accordance with the provider/subscriber model utilizedwhen the site was set up, the particular site may be a subscriber tomultiple providers, and those linkages are identified for furtherprocessing. From block 538, the flow passes to decision block 540. Indecision block 540, it is determined whether the source content itemsneed to be hidden. If they do, flow passes to block 542 wherein thesource contents are marked (flagged) with a HIDE action. From block 542,the flow passes to decision block 544. If the source content items donot require hiding, then the flow passes directly from decision block540 to decision block 544. In decision block 544, it is determinedwhether the source content data items can be directly copied to thetarget site without modification. If it can, then the flow passes toblock 546 wherein the contents are marked with a COPY action. From block546, the flow passes to decision block 548. If in decision block 544,the data items could not be directly copied, then the flow also passesto decision block 548. In decision block 548, it is determined whetherthe data items need to be translated. If they do, the flow passes toblock 550 wherein the data items are marked with a TRANSLATE action.From block 550, the flow passes to decision block 552, as does the flowfrom decision block 548 where the data items do not require translation.In block 552, it is determined whether the data items need to be changedbefore they are copied. If they do, then the flow passes to block 554wherein the data items are marked with a LOCALIZE action. From block544, the flow passes to block 556. If the data items did not requiremodification prior to copying, then the flow from block 552 passes toblock 556, wherein the process passes back to block 484 of FIG. 12. Notethat Hide, Copy, Localize, and Translate are examples of business rules.Any other business rules, such as Search and Replace, can beincorporated into the process steps discussed in preceding paragraphs.

In FIG. 16, the flow chart for the project management process is shown.From the start block 560, the flow passes to decision block 562 whereinit is determined whether or not a new project is being processed. If anew project is being processed, the flow passes from block 562 to block564. In block 564, a new project name and description is created. Flowpasses then from block 564 to block 566 wherein a recurring projectschedule is set up. From block 566, the flow passes to block 568,wherein the project actions are set up. The process of setting upproject actions will be further described in following paragraphs. Fromblock 568, the flow passes to block 570 wherein a workflow template isidentified with the project. The workflow template is an identificationof the process steps needed for the project including identification ofvendors for providing translation and review services. From block 570,the flow passes to block 572 wherein the workflow daemon is launched toautomatically handle the workflow process. From block 572, the flow thenpasses to decision block 574. If in decision block 562, the project wasnot identified as a new project, then the flow from decision block 562would also flow to decision block 574.

In decision block 574, it is determined whether the site-to-siterelationships have been assigned to the particular project. If it hasnot, the flow passes to block 588. If the site-to-site relationshipshave been defined, then the flow passes to decision block 576. Indecision block 576 it is determined whether the project daemon hasdetected that the current time coincides with a scheduled resourcechange detection time period of the project schedule. If it has not,this test is repeated until concurrence of the current time with thescheduled change detection schedule occurs. When concurrence isdetected, the flow passes from block 576 to block 578. In block 578, theautomatic detection of a resource change of the provider data source isperformed and then flow passes to decision block 580. In block 580, itis determined whether there has been a change in the source content. Ifno change is detected, the flow then passes back to decision block 576to repeat the sequence at the next scheduled time period. If, however, achange is detected, the flow passes from decision block 580 to block582. In block 582, the project actions are executed to appropriatelytransfer the resource, either directly, translated, or localized, fromthe source to the subscriber. From block 582, the flow passes todecision block 584 wherein it is determined whether the project actionhas been completed. If it has not, then the flow passes to block 586wherein the process is put on hold until the project actions have beencompleted. From block 586, the flow passes to block 588, as does theflow from decision block 584 if it is determined therein that theproject action had finished. In block 588, the user is able to view thecurrent or previous project status. From block 588, the flow passes toblock 590, which transfers the flow back to block 486 of FIG. 12.

The process in setting up project actions is illustrated in FIG. 17.From the start block 592, the flow passes to decision block 594 whereinit is determined whether the source content data items are marked with aHIDE action. If they are, flow passes to block 596, which essentiallytransfers the flow to decision block 598 without taking any action. Ifthe source content data items are not marked with a HIDE action, theflow also passes to decision block 598, wherein it is determined whetherthe source content data items are marked with a COPY action. If they aremarked with a COPY action, then the flow passes to block 600 wherein thesource content is copied into the local staging area of the target site.From block 600, the flow then passes to decision block 602, as does theflow from block 598 if the source content data items are not marked witha COPY action. In decision block 602, it is determined whether thesource content data items need to be translated prior to theirdeployment, transfer to the subscriber site. If translation is required,the flow passes to block 604 wherein the translation process isundertaken. Subsequent to completion of the translation process, theflow passes from block 604 to decision block 606. If translation was notrequired, then the flow from decision block 602 then passes to decisionblock 606, as well. Decision block 606 determines whether the sourcecontent data items need to be changed (localized) and deployed. Ifchange is required, the flow passes to block 608, wherein the sourcecontent data items are sent to local content editors who perform thelocalization necessary for the locale associated with the web site. Ifthe source does not require modification, the flow passes from decisionblock 606 to block 610, as does the flow from block 608. In block 610,the new contents is forwarded to local reviewers or marketers to insurethe content is proper for the locale. From block 610, the flow passes todecision block 612 wherein it is determined whether the local reviewersor marketers have approved the new contents. If they have not approvedthose contents, flow passes to block 614, wherein the contents arefurther modified in accordance with the requirements of the reviewers ormarketers and then the flow passes back to block 610. If it isdetermined that the new contents have been approved, then the flowpasses from block 612 to block 616. In block 616, the new content islabeled as such. From block 616, the flow passes to block 618. In block618, the appropriate target application interface is initiated to insertthe new content into the target space. From block 618, the flow passesto block 620 wherein the process passes back to block 568 of FIG. 16.

Turning now to FIG. 18, there is shown a flow chart for the globalresource translation process. From the starting point of block 622, theflow passes to block 624. In block 624, the project daemon automaticallycreates the ordering information and submits such to the electronictranslation portal. From block 624, the flow passes to decision block626, wherein it is determined whether the order had been submitted. Ifthe order was not submitted, the flow passes to block 628, wherein ordersubmission error handling procedures are carried out. From block 628,the flow passes back to block 624. If it is determined in decision block626 that the order has been submitted, then the flow passes to block 630wherein the files to be translated are copied and uploaded to theelectronic translation portal. From block 630, the flow passes todecision block 632, wherein it is determined whether the files have beenuploaded. If the uploading has not occurred, the flow passes to block634, wherein the file uploading error handling procedures are carriedout. From block 634, the flow passes back to block 630. If the fileshave been successfully uploaded, then the flow passes from decisionblock 632 to block 636. In block 626, the process is put on hold untilthe electronic translation portal indicates that the translations havebeen completed. From block 636, the flow passes to block 638 wherein thetranslated files are downloaded from the electronic translation portalinto a local staging area. From block 638, the flow passes to thedecision block 640. Decision block 640 determines whether the files havebeen successfully downloaded. If they have not, the flow passes to block642 wherein error handling procedures for downloading files is carriedout. From block 642, the flow passes back to block 638. If decisionblock 640 determines that the files have been successfully downloaded,the flow then passes to block 644 wherein the process is returned toblock 604 of FIG. 17.

Although this invention has been described in connection with specificforms and embodiments thereof, it will be appreciated that variousmodifications other than those discussed above may be resorted towithout departing from the spirit or scope of the invention. Forexample, equivalent elements may be substituted for those specificallyshown and described, certain features may be used independently of otherfeatures, and in certain cases, particular locations of elements may bereversed or interposed, all without departing from the spirit or scopeof the invention as defined in the appended Claims.

What is claimed is:
 1. A method for globalization management formaintaining resources between a plurality of websites, each of thewebsites including source content resources and in communication via anetwork with other websites of the plurality of websites, the methodcomprising: performing auto change detection to automatically detectupdates to source content resources at a first website of the pluralityof websites; determining whether a change in the source contentresources of the first website has occurred as a result of the updates;creating a workflow process for translating the changed source contentresources using a workflow template, the workflow template identifyingprocess steps for translating the source content resources, includingidentifying vendors for providing language translation and reviewservices of the changed source content resources; receiving atranslation of the changed source content resources using the workflowtemplate; receiving an approval of the received translation; andtransferring the translation of the changed source content resourcesusing a globalization management system via the network to a secondwebsite of the plurality of websites.
 2. The method of claim 1 whereinthe determining is performed through a target application interface. 3.The method of claim 2 wherein the target application interface iscustomized to deal with at least one of a vignette data source, aninterwoven data source, a database data source, or a file data source.4. The method of claim 1 wherein the determining whether the change inthe source content resources of the first website has occurred furthercomprises differentiating a local source content resource from a globalsource content resource.
 5. The method of claim 4 wherein the localsource content resource comprises at least one of a holiday promotion, acolloquialism, local culture, or local business customs.
 6. The methodof claim 1, the method being executed using the globalization managementsystem, further comprising managing a user's access to the globalizationmanagement system.
 7. The method of claim 6 wherein managing the user'saccess comprises assigning a role to the user.
 8. A method forglobalization management for maintaining resources between a pluralityof websites, each of the websites including source content resources andin communication via a network with other websites of the plurality ofwebsites, the method comprising: performing auto change detection toautomatically detect updates to source content resources at a firstwebsite of the plurality of websites; upon determining that a change inthe source content resources of the first website has occurred as aresult of the updates; creating a workflow process for translating thechanged source content resources using a workflow template, the workflowtemplate identifying process steps for translating the source contentresources, including identifying vendors for providing languagetranslation and review services of the changed source content resources;receiving a translation of the changed source content resources of thefirst website using the workflow template; receiving an approval of thereceived translation; and transferring the translation of the changedsource content resources using a globalization management system via thenetwork to a second website of the plurality of websites.
 9. The methodof claim 8 further comprising: performing another auto change detectionto automatically detect updates to source content resources at thesecond website of the plurality of websites; upon determining that achange in the source content resources of the second website hasoccurred as a result of the updates, creating a workflow process fortranslating the changed source content resources of the second websiteusing the workflow template; receiving a translation of the changedsource content resources of the second website using the workflowtemplate; and transferring the translation of the changed source contentresources using the globalization management system to the first websiteof the plurality of websites via the network.
 10. The method of claim 9wherein a target application interface is customized to deal with atleast one of a vignette data source, an interwoven data source, adatabase data source, or a file data source.
 11. The method of claim 8wherein the determining that the change in the source content resourcesof the first website has occurred further comprises differentiating alocal source content resource from a global source content resource. 12.The method of claim 11 wherein the local source content resourcecomprises at least one of a holiday promotion, a colloquialism, localculture, or local business customs.
 13. The method of claim 8, themethod being executed using the globalization management system, furthercomprising managing a user's access to the globalization managementsystem.
 14. The method of claim 13 wherein managing the user's accesscomprises assigning a role to the user.
 15. A globalization managementsystem for maintaining resources between a plurality of websites, eachof the websites including source content resources and in communicationvia a network with other websites of the plurality of websites, thesystem comprising: a processor configured to execute instructions storedin memory; and a memory, coupled to the processor, the memory comprisinginstructions executable by the processor to: perform auto changedetection to automatically detect updates to source content resources ata first website of the plurality of websites; determine whether a changein the source content resources of the first website has occurred as aresult of the updates; create a workflow process for translating thechanged source content resources using a workflow template, the workflowtemplate identifying process steps for translating the source contentresources, including identifying vendors for providing languagetranslation and review services of the changed source content resources;receive a translation of the changed source content resources using theworkflow template; receive an approval of the received translation; andtransfer the translation of the changed source content resources using aglobalization management system via the network to a second website ofthe plurality of websites.
 16. The system of claim 15 wherein theinstructions to determine whether a change in the source contentresources of the first website has occurred further compriseinstructions for a target application interface.
 17. The system of claim15 wherein the instructions to determine whether a change in the sourcecontent resources of the first website has occurred further compriseinstructions to differentiate a local source content resource from aglobal source content resource.
 18. The system of claim 17 wherein thelocal source content resource comprises at least one of a holidaypromotion, a colloquialism, local culture, or local business customs.19. The system of claim 15 wherein the instructions further compriseinstructions to manage a user's access to the globalization managementsystem.
 20. The system of claim 19 wherein the instructions to managethe user's access further comprise instructions to assign a role to theuser.